Adds .vue functionality #77

prograhammer · 2017-11-29T08:41:02Z

Hi guys,

This PR adds ability to work with .vue files (see #70).

For a quick test, I created a vue branch (out of the feature/vue branch) with the built lib folder included. So you can install like this:

npm install git://github.com/prograhammer/fork-ts-checker-webpack-plugin.git#vue --save-dev

Turn on the vue option in the plugin in your webpack config:

    new ForkTsCheckerWebpackPlugin({
      tslint: true,
      vue: true
    })

For linting to work in .vue files, you need to ensure your script tag's language attribute is set
to ts or tsx (also make sure you include the .vue extension in all your import statements as shown below):

<script lang="ts">
import Hello from '@/components/hello.vue'

// ...

</script>

If you are testing in Webpack, (in addition to this plugin) you'll need something like this in your rules:

{
  test: /\.ts$/,
  loader: 'ts-loader',
  include: [resolve('src'), resolve('test')],
  options: {
    appendTsSuffixTo: [/\.vue$/],
    transpileOnly: true
  }
},
{
  test: /\.vue$/,
  loader: 'vue-loader',
  options: vueLoaderConfig
},

I also currently use tslint-config-standard so my tslint.json looks something like:

{
    "defaultSeverity": "error",
    "extends": [
      "tslint-config-standard"
    ]
}

Ensure your tsconfig.json doesn't exclude .vue files:

// tsconfig.json
{
  "include": [
    "src/**/*.ts",
    "src/**/*.vue"
  ],
  "exclude": [
      "node_modules"
  ],
  "compilerOptions": {
    
    // ...

    "baseUrl": ".",
    "paths": {
      "@/*": [
        "src/*"
      ]
    }
  }
}

If you are working in VSCode, you'll need extensions Vetur and TSLint Vue (a forked extension which I also currently maintain) and the editor will match the output you get from this fork-ts-checker-webpack-plugin.

Let me know what more you need or if you have any suggestions on code improvement/cleanup/etc.

Thanks!

johnnyreilly · 2017-11-29T08:58:52Z

First of all: good work! What I say should be taken with a pinch of salt as I'm not a maintainer of this plugin.

That aside, I notice that with the current approach the code moves to always bring Vue into the mix. I'd be tempted to refactor the code to only use the Vue approach when you are definitely using the Vue functionality. Essentially treating the Vue functionality as something that can be feature flagged on or off. Do you understand what I mean? (I may not be being super clear)

prograhammer · 2017-11-29T09:10:32Z

@johnnyreilly Yeah I was thinking about that too. Do you think a flag to turn it on via the plugin options would be the way to go?

johnnyreilly · 2017-11-29T10:15:14Z

I think that might be an idea (unless it can be reliably inferred somehow - possibly from the presence of 'vue' in compiler.options.resolve.extensions?)

Toilal · 2017-11-29T20:21:51Z

src/IncrementalChecker.ts

+  * Assumes wildcard "@" is [project root]/src.
+  */
+  static resolveNonTsModuleName(moduleName: string, containingFile: string, programConfigFile: string): string {
+    if (moduleName.indexOf('@/') === 0) {


Instead of hardcoded values, both webpack configuration (resolve.alias, resolve.modules) and tsconfig parameters (baseUrl and paths option) could be exploited here.

Toilal · 2017-11-29T20:22:51Z

src/IncrementalChecker.ts

@@ -9,6 +9,7 @@ import WorkSet = require('./WorkSet');
 import NormalizedMessage = require('./NormalizedMessage');
 import CancellationToken = require('./CancellationToken');
 import minimatch = require('minimatch');
+import vueParser = require('vue-parser');


It would be better to use vue-template-compiler parseComponent function. Return type is SFCDescriptor, see flow typings https://github.com/vuejs/vue/blob/dev/flow/compiler.js#L172-L177

Toilal · 2017-11-30T09:06:19Z

I don't think we can rely on compiler.options.resolve.extensions because most ts-loader users enable appendTsSuffixTo to make *.vue files looks like *.ts files. (https://github.com/TypeStrong/ts-loader#appendtsxsuffixto-regexp-default)

johnnyreilly · 2017-11-30T09:30:50Z

Fair point - maybe an explicit flag is better

Toilal · 2017-11-30T09:32:38Z

Maybe we can check vue-loader is available by trying to simply trying to require it ...

prograhammer · 2017-11-30T10:55:38Z

@Toilal That's a pretty clever idea (smart detection).

How do you guys feel about me moving all of this code into a separate module called CreateVueProgram.ts. I'll restore the code back to the way it was before the PR and just use a condition to decide whether to call CreateVueProgram here: https://github.com/Realytics/fork-ts-checker-webpack-plugin/blob/master/src/IncrementalChecker.ts#L161

There's no reason to be super DRY here. We can let Vue be its own thing and go it's own path by taking care of it in it's own module. Leave the normal program as it was in IncrementalChecker before I touched it. Then I'll start applying all those suggestions you made throughout the code @Toilal.

Thoughts?
Cc @johnnyreilly

johnnyreilly · 2017-11-30T16:28:03Z

Sounds promising!

prograhammer · 2017-12-01T14:32:11Z

Alright guys,

Everything works great on my example project on my local machine because the project is a Vue project with vue-loader in it's node_modules. You can see I added the condition here. But Travis fails because I imagine there's no vue-loader in the project it is testing with. This is a nice approach, but what should we do about Travis? Or should we do something else instead, like check for an option from the plugin?

Update: Nevermind! facepalm Thanks @Toilal

Toilal · 2017-12-01T14:53:11Z

src/IncrementalChecker.ts

+    const projectPath = path.dirname(this.programConfigFile);
+    const contextResolution = Resolve.sync('vue-loader', { basedir: projectPath });
+
+    return require(contextResolution) ? true : false;


It seems you still have to try/catch this line and return false on error ...

Oh right! Brain freeze! Of course that's the problem. LOL. Will fix...

prograhammer · 2017-12-01T16:47:28Z

voila! @Toilal !

All checks passing now. I'll merge master into it (and fix any conflicts) after all feedback is in. Now regarding feedback, I looked over webpack resolve and so far I don't really see any API documentation around that for using it programmatically. Also, for vue-template-compiler there are no types defined. We just need a fast AST tree parser and that's what vue-parser is doing here (uses parse5 under the hood).

prograhammer · 2017-12-01T17:05:37Z

Alright guys, there's a huge line of eager people waiting for this (there's over 1,300 people who have TSLint Vue currently installed in their VSCode editor and those Vue folks are almost all guaranteed to be on Webpack). And there's no other option availabe for Vue developers that runs at the typechecker level. Since I've split off the code so it doesn't disrupt the original program, what can we do to fast-track this PR? I'll continue to help polish things up afterwards as well.

johnnyreilly · 2017-12-01T18:17:06Z

@prograhammer the person who needs to feed back is @piotr-oles. This is his project and only he can merge I'm afraid. In the short term you could consider publishing the fork to a GitHub repo with the compiled dist included as well. We did that whilst we were waiting for 0.2.9 to be published. See here: https://github.com/TypeStrong/fork-ts-checker-webpack-plugin

Speaking of which, I must take that down now 0.2.9 has shipped.

johnnyreilly · 2017-12-01T18:26:49Z

Background to how that came to pass here: #64

prograhammer · 2017-12-01T18:31:14Z

Ah, gotcha. No worries!

Yeah I've got this branch here that I'll keep promoting to folks in the meantime: npm install git://github.com/prograhammer/fork-ts-checker-webpack-plugin.git#vue --save-dev

johnnyreilly · 2017-12-01T19:24:24Z

Sweet!

johnnyreilly · 2017-12-03T07:03:06Z

src/IncrementalChecker.ts

  }

  nextIteration() {
    if (!this.watcher) {
-      this.watcher = new FilesWatcher(this.watchPaths, ['.ts', '.tsx']);
+      this.watcher = new FilesWatcher(this.watchPaths, ['.ts', '.tsx', '.vue']);


Could the .vue be conditional based on whether vue is in the mix or not please?

johnnyreilly · 2017-12-03T07:04:33Z

src/IncrementalChecker.ts

  nextIteration() {
    if (!this.watcher) {
-      this.watcher = new FilesWatcher(this.watchPaths, ['.ts', '.tsx']);
+      this.watcher = new FilesWatcher(this.watchPaths, ['.ts', '.tsx', '.vue']);


Could including vue be conditional upon whether this is a vue program or not please?

Does it hurt to always include .vue? It doesn't really bother the folks not on Vue.js. Otherwise it's another condition we'll need to make here for the watcher. Thoughts?

2 things really:

It will make a marginal speed difference for non-Vue users. I'm philosophically opposed to that 😄

It bothers me on an OCD level that Vue files would be always in the mix when they needn't be. This is more subjective I grant you but makes me twitch in unhappy ways. It is my suffering.

There's always a battle between code readability and micro-optimization (in this case the optimization may be significant). OCD kicks in for both 😄
But let me see of a clean way to condition that...

Thanks man!

johnnyreilly · 2017-12-03T07:05:41Z

src/IncrementalChecker.ts

@@ -158,7 +176,14 @@ class IncrementalChecker {
      }
    }

-    this.program = IncrementalChecker.createProgram(this.programConfig, this.files, this.watcher, this.program);
+    if (this.hasVueLoader()) {
+      this.programConfig = this.programConfig || VueProgram.loadProgramConfig(this.programConfigFile);


in this branch isn't it always the VueProgram you use?

No no, this condition is here to detect if vue-loader is found in the user's project and then use the VueProgram if it is. We don't need to maintain a separate branch for Vue if we have this condition. It can be merged into master.

this.programConfig || VueProgram.loadProgramConfig(this.programConfigFile) but wouldn't this statement always use programConfig? Or have I missed something?

The first pass over that line this.programConfig will be undefined so it will grab the return from the right side of the condition (VueProgram.loadProgramConfig(...). The next time it passes over that line this.programConfig will have a value and it will grab that instead of performing another unnecessary VueProgram.loadProgramConfig(....

Cool - WFM!

johnnyreilly · 2017-12-03T07:08:36Z

It's looking good @prograhammer - I've a few comments as you can see but it's basically good. I'm glad that this is mostly triggered only when Vue is in the mix.

@piotr-oles would you be able to take a look at this when you get a mo?

jthomaschewski · 2017-12-04T15:16:15Z

Thanks for the effort @prograhammer
I tried using your fork in a project of mine but I have problems with mixed JS/TS vue components.

When importing a JSModule.vue module with <script> from a TSModule.vue module with <script lang="ts"> (or any .ts file) I get:

ERROR in /app/TSModule.vue(2,27):
TS2306: File '/app/JSModule.vue' is not a module.

Same result regardless of allowJs setting in tsconfig.json.
No issues when running tsc -p . --noEmit or ts-loader withtranspileOnly: false

Importing vue components with TS works fine from both plain .ts and ts-enabled .vue files

EDIT:
Importing such JS vue modules does work when using absolute paths, e.g @/components/JSModule.vue. But I would expect this to also work with relative paths as I have the following declaration file for Vue:

declare module '*.vue' {
  import Vue from 'vue'
  export default Vue
}

CKGrafico · 2017-12-05T17:27:25Z

Please accept that!

prograhammer · 2017-12-05T18:51:07Z

@JBBr A couple things to point out here:

You don't need that wildcard declaration (declare module '*.vue' ...). That defeats the purpose of this PR and TypeScript. You won't get full type information from your Vue modules if you do that.
You need to ensure your scripts have lang="ts" or lang="tsx" for them to be parsed. I just updated the code to allow js and jsx as well, but that doesn't seem like your problem.
The code works for relative paths too. Maybe something else is going on. The best way to know is to give us an example project repo on Github we can pull down and see the problem.

…r-webpack-plugin#77

prograhammer · 2017-12-05T19:25:42Z

@johnnyreilly All your feedback is all done brother, 😸

prograhammer · 2018-01-01T23:17:09Z

Hi @Punit-wingify

I can confirm in my own project that I am able to access this.$store.state.some.foo and it works perfectly with this PR. Make sure you have the latest Vue and Vuex. You can see here that when you add Vuex to your project the Vue type interface is extended to include $store: Store<any>.

Punit-wingify · 2018-01-02T06:15:33Z

@prograhammer Okay thanks, just needed the confirmation 👍

TheLarkInn · 2018-01-06T00:12:17Z

Anything we [at webpack] can help with furthering this along. This is super exciting and we've heard a few downstream requests come our way in regards to its status.

Happy to help in any way possible or unblock any blockers if they exist.

johnnyreilly · 2018-01-06T06:58:57Z

Thanks @TheLarkInn - that's always appreciated!

I think the current status is that @prograhammer has fixed all the issues we're aware of and the only thing we're waiting on is @piotr-oles to confirm he's happy to merge. Exciting!

@piotr-oles are we ready to go now?

keenwon · 2018-01-08T12:47:42Z

@prograhammer

After turn on the vue option, I got a error:

new ForkTsCheckerWebpackPlugin({
  vue: true
})

{
  test: /\.ts$/,
  exclude: /node_modules|vue\/src/,
  loader: 'ts-loader',
  options: {
    transpileOnly: true,
    appendTsSuffixTo: [/\.vue$/]
  }
},
{
  test: /\.vue$/,
  loader: 'vue-loader',
  options: {
    esModule: true,
    loaders: {
      ts: 'ts-loader',
      scss: 'vue-style-loader!css-loader!sass-loader'
    }
  }
}

Starting type checking service...
Using 1 worker with 2048MB memory limit
webpack building...
D:\Code\nei7\node_modules\fork-ts-checker-webpack-plugin\lib\service.js:22
        throw error;
        ^

TypeError: Cannot read property 'flags' of undefined
    at getBaseTypes (D:\Code\nei7\node_modules\typescript\lib\typescript.js:28172:37)
    at getSuperClass (D:\Code\nei7\node_modules\typescript\lib\typescript.js:37548:21)
    at isPropertyDeclaredInAncestorClass (D:\Code\nei7\node_modules\typescript\lib\typescript.js:37537:29)
    at checkPropertyNotUsedBeforeDeclaration (D:\Code\nei7\node_modules\typescript\lib\typescript.js:37507:21)
    at checkPropertyAccessExpressionOrQualifiedName (D:\Code\nei7\node_modules\typescript\lib\typescript.js:37477:13)
    at checkPropertyAccessExpression (D:\Code\nei7\node_modules\typescript\lib\typescript.js:37448:20)
    at checkExpressionWorker (D:\Code\nei7\node_modules\typescript\lib\typescript.js:40582:28)
    at checkExpression (D:\Code\nei7\node_modules\typescript\lib\typescript.js:40529:42)
    at checkExpressionCached (D:\Code\nei7\node_modules\typescript\lib\typescript.js:40406:38)
    at checkVariableLikeDeclaration (D:\Code\nei7\node_modules\typescript\lib\typescript.js:42623:43)

prograhammer · 2018-01-08T18:48:22Z

Hi @keenwon

Instead of passing Vue files to ts-loader from vue-loader, try updating your vue-loader options to look like this:

    loaders: {
      // ts: 'ts-loader',  <-- remove this
      scss: 'vue-style-loader!css-loader!sass-loader'
    }

And then you would need to update your ts-loader exclude statement (try an include statement as shown in the first post).
Are using this build: npm install git://github.com/prograhammer/fork-ts-checker-webpack-plugin.git#vue --save-dev?
Create a simplified example project (strip everything down, remove your biz logic or whatever) on your Github and give us a link to it here so we can diagnose the error first hand with what you are doing in the project.

piotr-oles · 2018-01-09T19:48:02Z

Looks good, will be released as 0.3.0 :) Great work!

keenwon · 2018-01-10T02:35:07Z

@prograhammer this project can reproduce the problem.
https://github.com/keenwon/fork-ts-checker-webpack-plugin-test

prograhammer · 2018-01-10T06:59:47Z

@keenwon

It looks like you found a strange TypeScript bug which is not coming from fork-ts-checker-webpack-plugin (previous version or latest 0.3.0 with Vue functionality) but rather TypeScript itself (even the latest TypeScript version). The reason you are seeing it when you turn on the vue flag is not due to fork-ts-checker-webpack-plugin but is because of that specific type of error inside the class (with the experimental decorator) in that Vue file...

For example, take this class with the error Block-scoped variable 'bar' used before its declaration:

import Vue from 'vue'
import { Component, Prop, Watch } from 'vue-property-decorator'

@Component
export default class Test extends Vue {
  public foo: string = this.bar  // <-- This is an error that TypeScript can handle. Decorator may be the problem.
  private bar: string
}

and put it in a regular .ts file such as test.ts and import it into your main entry. Remove fork-ts-checker-webpack-plugin completely from your webpack config and then update ts-loader (remove the transpileOnly) to compile. You'll see TypeScript still breaks on that code. It even breaks the normal (non-Vue) TSLint extension in VSCode.

I'll report the issue to TypeScript (as well as look into it myself) and put the link here for anyone to follow. In the mean time, just fix that error in that class. Let us know if anything else breaks, thanks!

johnnyreilly · 2018-01-10T07:36:30Z

Perhaps a silly question, but why not just swap the foo and bar lines? It seems like a legitimate TypeScript error to me...

prograhammer · 2018-01-10T07:40:03Z

Yeah but it's an error TypeScript should be able to handle without breaking. It handles this error fine outside of experimental decorators (reports it as Block-scoped variable 'bar' used before its declaration). 😢 But all other errors seem to work fine in experimental decorators.

johnnyreilly · 2018-01-10T08:05:24Z

Hmmm weird - definitely report it on the Typescript repo I reckon

Toilal · 2018-01-10T08:42:31Z

I tried the new release with vue: true and tslint: true, and it works really well.

Only issue I found i that linter is running on empty script tag content, even when a src attribute is defined.

<template src="./App.html"></template>
<style scoped src="./App.css"></style>
<script lang="ts" src="./App.ts"></script>

This raises tslint errors for missing EOL

ERROR in C:/devel/projects/vue-ts-test/src/App.vue
(3,91): file should end with a newline

CKGrafico · 2018-01-10T10:48:55Z

@Toilal can you upload your working example? in my nuxt project linting is still not working on vue files :/
About EOL I think that is a rule that has sense 4-5 years ago but now I usually disable it.

In my case
Working
import SkipLink from './SkipLink.vue';
Not working
import SkipLink from '~/components/SkipLink.vue';

But if I disable this plugin, everything is working

CKGrafico · 2018-01-10T14:28:31Z

Wow ok my error is here... @prograhammer https://github.com/Realytics/fork-ts-checker-webpack-plugin/pull/77/files#r159148429 haha '~' is super common to! (In Microsoft environments more) I'll made a PR for this :D

prograhammer · 2018-01-10T22:57:31Z

@Toilal

That's weird since vue-parser adds an EOL here: https://github.com/prograhammer/vue-parser/blob/master/src/index.ts#L27

Maybe it's complaining about the Vue file itself. Can you add an EOL to it and see what happens:

<template src="./App.html"></template>
<style scoped src="./App.css"></style>
<script lang="ts" src="./App.ts"></script>
<-- EOL here

prograhammer · 2018-01-10T22:59:10Z

@CKGrafico Of course you know what the best solution is right? Switch to Ubuntu Gnome 3 for development (and dual boot with Windows for gaming/photoshop/etc.). 😆 😆 😆

Toilal · 2018-01-11T19:48:24Z

I can't reproduce the EOL issue now ... Maybe after upgrading to tslint 5.9.1 ? (5.9.0 was broken at release, but shortly fixed)

…r-webpack-plugin#77

prograhammer mentioned this pull request Nov 29, 2017

curious if this plugin works with vue and typescript? #70

Closed

Toilal reviewed Nov 29, 2017

View reviewed changes

Toilal reviewed Dec 1, 2017

View reviewed changes

johnnyreilly reviewed Dec 3, 2017

View reviewed changes

This was referenced Dec 4, 2017

Support linting vue/html file palantir/tslint#2099

Closed

Linting support for typescript vuejs/vetur#170

Open

CKGrafico added a commit to pwa-builder/PWABuilder that referenced this pull request Dec 5, 2017

Temporary disable linting of TS waiting for TypeStrong/fork-ts-checke…

8063ee5

…r-webpack-plugin#77

Toilal mentioned this pull request Jan 5, 2018

can we create real single component vue file? Toilal/vue-webpack-template#57

Closed

prograhammer mentioned this pull request Jan 5, 2018

Minimal TypeScript support option added vuejs-templates/webpack#797

Open

piotr-oles approved these changes Jan 9, 2018

View reviewed changes

piotr-oles changed the base branch from next to master January 9, 2018 19:43

Merge branch 'master' into feature/vue

57f2320

piotr-oles merged commit 48055c6 into TypeStrong:master Jan 9, 2018

CKGrafico mentioned this pull request Jan 10, 2018

Add options to wildcard #86

Merged

ColCh mentioned this pull request Mar 23, 2018

TypeScript types got broken by this project installation #107

Closed

kuoruan mentioned this pull request Jun 20, 2018

vue-loader 15 with TypeScript & webpack causes tslint to fail on .vue files. vuejs/vue-loader#1304

Open

lucaasrojas pushed a commit to southworks/monorepo that referenced this pull request Mar 21, 2019

Temporary disable linting of TS waiting for TypeStrong/fork-ts-checke…

417be0c

…r-webpack-plugin#77

agilgur5 mentioned this pull request Sep 11, 2022

Importing Vue SFC from lang="ts" block ezolenko/rollup-plugin-typescript2#129

Open

Adds .vue functionality #77

Adds .vue functionality #77

Conversation

prograhammer commented Nov 29, 2017 • edited Loading

johnnyreilly commented Nov 29, 2017

prograhammer commented Nov 29, 2017 • edited Loading

johnnyreilly commented Nov 29, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Toilal commented Nov 30, 2017

johnnyreilly commented Nov 30, 2017

Toilal commented Nov 30, 2017

prograhammer commented Nov 30, 2017 • edited Loading

johnnyreilly commented Nov 30, 2017

prograhammer commented Dec 1, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

prograhammer commented Dec 1, 2017 • edited Loading

prograhammer commented Dec 1, 2017 • edited Loading

johnnyreilly commented Dec 1, 2017

johnnyreilly commented Dec 1, 2017

prograhammer commented Dec 1, 2017

johnnyreilly commented Dec 1, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

prograhammer Dec 4, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

prograhammer Dec 4, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

johnnyreilly commented Dec 3, 2017

jthomaschewski commented Dec 4, 2017 • edited Loading

CKGrafico commented Dec 5, 2017

prograhammer commented Dec 5, 2017 • edited Loading

prograhammer commented Dec 5, 2017 • edited Loading

prograhammer commented Jan 1, 2018 • edited Loading

Punit-wingify commented Jan 2, 2018

TheLarkInn commented Jan 6, 2018

johnnyreilly commented Jan 6, 2018 • edited Loading

keenwon commented Jan 8, 2018

prograhammer commented Jan 8, 2018 • edited Loading

piotr-oles commented Jan 9, 2018

keenwon commented Jan 10, 2018 • edited Loading

prograhammer commented Jan 10, 2018 • edited Loading

johnnyreilly commented Jan 10, 2018

prograhammer commented Jan 10, 2018 • edited Loading

johnnyreilly commented Jan 10, 2018

Toilal commented Jan 10, 2018

CKGrafico commented Jan 10, 2018 • edited Loading

CKGrafico commented Jan 10, 2018

prograhammer commented Jan 10, 2018 • edited Loading

prograhammer commented Jan 10, 2018

Toilal commented Jan 11, 2018

prograhammer commented Nov 29, 2017 •

edited

Loading

prograhammer commented Nov 29, 2017 •

edited

Loading

prograhammer commented Nov 30, 2017 •

edited

Loading

prograhammer commented Dec 1, 2017 •

edited

Loading

prograhammer commented Dec 1, 2017 •

edited

Loading

prograhammer commented Dec 1, 2017 •

edited

Loading

prograhammer Dec 4, 2017 •

edited

Loading

prograhammer Dec 4, 2017 •

edited

Loading

jthomaschewski commented Dec 4, 2017 •

edited

Loading

prograhammer commented Dec 5, 2017 •

edited

Loading

prograhammer commented Dec 5, 2017 •

edited

Loading

prograhammer commented Jan 1, 2018 •

edited

Loading

johnnyreilly commented Jan 6, 2018 •

edited

Loading

prograhammer commented Jan 8, 2018 •

edited

Loading

keenwon commented Jan 10, 2018 •

edited

Loading

prograhammer commented Jan 10, 2018 •

edited

Loading

prograhammer commented Jan 10, 2018 •

edited

Loading

CKGrafico commented Jan 10, 2018 •

edited

Loading

prograhammer commented Jan 10, 2018 •

edited

Loading